1 # Migrating from baseflight
5 **First ensure your main flight battery is disconnected or your props are off!**
7 Before flashing with cleanflight, dump your configs for each profile via the CLI and save to a text file.
18 Then after flashing cleanflight paste the output from each dump command into the cli, switching profiles as you go.
20 You'll note that some commands are not recognised by cleanflight when you do this. For the commands that are not recognised look
21 up the new configuration options and choose appropriate values for the settings. See below for a list of differences.
23 Once you've done this for the first profile, save the config. Then verify your config is OK, e.g. features serial ports, etc.
24 When you've verified the first profile is OK repeat for the other profiles.
26 It's also advisable to take screenshots of your AUX settings from baseflight configurator and then after re-applying the settings
27 verify your aux config is correct - aux settings are not backwards compatible.
29 ## CLI command differences from baseflight
31 In general all CLI commands use underscore characters to separate words for consistency. In baseflight the format of CLI commands is somewhat haphazard.
34 reason: unified baud rate configuration
36 If an unsupported baud rate value is used the gps code will select 115200 baud.
38 see `serial_port_x_gps_baudrate`
41 reason: renamed to `gps_provider` for consistency
44 reason: renamed to `serialrx_provider` for consistency
47 reason: improved functionality
49 Cleanflight supports using any RX channel for rssi. Baseflight only supports AUX1 to 4.
51 In Cleanflight a value of 0 disables the feature, a higher value indicates the channel number to read RSSI information from.
53 Example: to use RSSI on AUX1 in Cleanflight use `set rssi_aux_channel = 5`, since 5 is the first AUX channel.
55 ### failsafe_detect_threshold
56 reason: improved functionality
58 See `failsafe_min_usec` and `failsafe_max_usec` in Failsafe documentation.
61 reason: renamed to `emf_avoidance` for consistency
64 reason: renamed to `yaw_rate` for consistency
67 reason: renamed to `yaw_deadband` for consistency
70 reason: renamed to `mid_rc` for consistency
73 reason: renamed to `min_check` for consistency
76 reason: renamed to `max_check` for consistency
79 reason: renamed to `min_throttle` for consistency
82 reason: renamed to `max_throttle` for consistency
85 reason: renamed to `min_command` for consistency
88 reason: renamed to `3d_deadband_low` for consistency
91 reason: renamed to `3d_deadband_high` for consistency
93 ### deadband3d_throttle
94 reason: renamed to `3d_deadband_throttle` for consistency
97 reason: renamed to `3d_neutral` for consistency
99 ### alt_hold_throttle_neutral
100 reason: renamed to `alt_hold_deadband` for consistency